The CI workflow was using Netlify deployment names that conflict with Netlify's built-in deploy-preview mechanism, causing HTML previews to not show the latest build correctly.

Problem

Netlify was showing this warning during deployments:

Using a branch name that starts with `deploy-preview-` can result in unexpected behavior

The CI workflow in .github/workflows/ci.yml was using:

--context deploy-preview \
--alias deploy-preview-${{ github.event.pull_request.number }} \

This naming pattern conflicts with Netlify's internal deploy-preview system, preventing the latest HTML builds from being properly displayed on PR preview links.

Solution

Changed the naming structure to avoid the conflict:

• --context deploy-preview → --context pr-preview
• --alias deploy-preview-${{ github.event.pull_request.number }} → --alias pr-${{ github.event.pull_request.number }}

Impact

• Resolves the Netlify naming conflict warning
• Ensures HTML previews show the latest build correctly
• Maintains all existing functionality - this is purely a naming change
• PR preview URLs will now use the pattern pr-123 instead of deploy-preview-123
• Manual deployments (using dev context) are unaffected

Fixes #607.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.